home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #14
/
Monster Media No. 14 (April 1996) (Monster Media, Inc.).ISO
/
bbs_door
/
ksphst12.zip
/
KSP-HOST.DOC
< prev
next >
Wrap
Text File
|
1996-02-11
|
48KB
|
1,453 lines
KSP-HOST (tm)
An Inbound Telnet Server
for
MS/DOS Bulletin Board Systems
Version 1.2
Copyright (C) 1995-96
All Rights Reserved
by
KEY SOFTWARE PRODUCTS
440 Ninth Avenue
Menlo Park, California 94025-1802
BBS/FAX: 415-364-9847
KSP-HOST, KSP-SRVR, KSP-CALL, and KSP-NODE
are trademarks of Key Software Products.
WATTCP is a trademark of Erick Engelke.
Power C and Multi-C are trademarks of Mix Software.
Lantastic is a trademark of Artisoft, Inc.
Novell is a trademark of Novell Corp.
Banyan Vines is a trademark of Banyan Inc.
DESQview is a trademark of Quarterdeck Office Systems.
TABLE OF CONTENTS
CHAPTER 1 - INTRODUCTION ........................... 1
1.1 Other KSP Software ........................... 2
1.1.1 KSP Telnet ............................. 2
1.1.2 KSP FTP ................................ 3
1.1.3 KSP SLIP ............................... 3
1.1.4 KSP Mail ............................... 3
1.1.5 So Many CD's ............................ 3
CHAPTER 2 - INSTALLING THE NETWORK CONNECTION FIRST .... 4
2.1 Packet Driver Shim for Novell .................. 4
2.2 Packet Driver Shim for Novell w/Token-Ring SNAP .. 5
2.3 Packet Driver Shim for Lantastic ............... 5
2.3.1 Changes to CONFIG.SYS ................... 5
2.3.2 Changes to PROTOCOL.INI ................. 6
2.4 Packet Driver Shim for Banyan Vines ............. 7
CHAPTER 3 - THE WATTCP CONFIGURATION FILE ............. 8
3.1 Network Parameters .......................... 9
3.1.1 The PC's Host Name ....................... 9
3.1.2 The PC's Domain Name ..................... 9
3.1.3 The PC's IP Address ...................... 9
3.1.4 The Name Server's IP Address .............. 10
3.1.5 The Router's IP Address .................. 10
3.1.6 The PC's Network Mask .................... 10
3.2 TCP/IP Parameters (optional) ................. 11
3.2.1 Timeouts .............................. 11
3.2.2 Maximum Segment Size (MSS) ............... 11
3.3 Parameters Specific to KSP Host ................ 11
3.3.1 The Log File Directory ................... 11
3.3.2 Retrieving Hostname of Remote Client ...... 12
3.3.3 Specifying the Fossil Ports .............. 12
3.3.4 Specifying the Buffer Size ............... 13
3.3.5 Maximum Number of Rings .................. 13
3.3.6 Sending a "CONNECT" string to the BBS ....... 13
3.3.7 Specifying Modem Delay .................. 14
3.3.8 Disabling Automatic Load High ............ 14
CHAPTER 4 - Programs in the KSP Host Package ............ 15
4.1 KSP-NODE (Installed on each BBS Machine) ........ 15
4.1.1 Command Line Parameters ................. 15
4.2 KSP-CALL (Used to Test KSP-NODE) ............... 16
4.2.1 Command Line Parameters ................. 16
4.3 KSP-SRVR (The Inbound Telnet Server) ........... 16
4.3.1 Command Line Parameters ................. 16
CHAPTER 5 - SPECIAL CONFIGURATION CONSIDERATIONS ..... 18
5.1 PCBoard .................................... 18
5.2 DESQview ................................... 18
TABLE OF CONTENTS
5.3 Novell ..................................... 18
APPENDIX 1 - HOW TO REACH US .......................... 20
APPENDIX 2 - GETTING UPDATES VIA THE INTERNET .......... 21
APPENDIX 3 - LEGAL STUFF ............................ 22
Feb 11, 1996 KSP-HOST (tm) v1.2 1
CHAPTER 1 - INTRODUCTION
KSP-HOST allows MS/DOS Bulletin Board Systems to accept inbound
Telnet connections. In addition to being able to contact your
BBS by modem, users can now connect to your BBS over the
Internet using Telnet.
The name "KSP-HOST" actualy refers to a pair of programs: A
program called KSP-SRVR handles reception of inbound Telnet
sessions and communicates with another program called KSP-NODE
running on each of your BBS nodes:
╔══════════╗
┌──────────────────────────────╢ KSP-SRVR ║
│ ──╢ ║
│ (NetBios) ──╢ ║───── Internet
│ ║ Telnet ║ (TCP/IP)
│ ┌──────────╢ Host ║
╔═════╧════╗ ╔═════╧════╗ ╚══════════╝
║ KSP-NODE ║ ... ║ KSP-NODE ║
╚═════╤════╝ ╚═════╤════╝
┌─────┴────┐ ┌─────┴────┐
│ BBS Prog │ ... │ BBS Prog │
│ (Node 1) │ │ (Node N) │
└──────────┘ └──────────┘
This arrangement allows Telnet users to use a single Internet IP
address or hostname (that of the machine running KSP-SRVR) to
contact your BBS. KSP-SRVR then determines which BBS nodes are
available, and routes the session to one of those nodes. As
implied, KSP-SRVR can handle multiple telnet connections at the
same time.
The above diagram illustrates how things are organized
logically; the actual physical organization is somewhat
different:
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 2
Local Ethernet (Novell, Artisoft, etc.)
──────────────┬───────────────────┬─────────┬─────────────┬─────
│ │ │ │
┌──────────┐ │ ┌──────────┐ │ ┌─────┴────┐ ┌────┴────┐
│ BBS Prog │ │ │ BBS Prog │ │ │ Packet │ │ Router │
│ (Node 1) │ │ │ (Node N) │ │ │ Driver │ │ E.g., │
└─────┬────┘ │ └─────┬────┘ │ └─────┬────┘ │ KA9Q NET│
│ │ │ │ │ └────┬────┘
╔═════╧════╗ │ ╔═════╧════╗ │ │ │
║ KSP-NODE ╟──┘ ║ KSP-NODE ╟──┘ ╔═════╧════╗ │
╚═════╤════╝ ╚═════╤════╝ ║ KSP-SRVR ║ │
│ │ ║ Telnet ║ Internet
┌─────┴────┐ ┌─────┴────┐ ║ Host ║ Connection
│ Fossil │ ... │ Fossil │ ╚══════════╝ (TCP/IP)
│ Driver │ ... │ Driver │
└─────┬────┘ └─────┬────┘
│ │
Modem Modem
As indicated, the small TSR program KSP-NODE, acts as a switch
so that each BBS node can accept either Telnet calls or regular
modem calls. This requires every BBS node to use a Fossil
driver as shown.
Communication between KSP-SRVR and KSP-NODE uses NetBios. I.e.,
KSP-SRVR is a protocol converter that translates Internet TCP/IP
packets into NetBios packets, and vice-versa. NetBios is
commonly supported by most local area network software such as
Lantastic or Novell.
The packet driver (or packet driver shim) is explained in the
next chapter; detailed information regarding the installation
and configuration of KSP-SRVR and KSP-NODE appears in subsequent
chapters.
The router shown above connects your local network to the
Internet; a shareware program called KA9Q NET can serve this
purpose.
1.1 Other KSP Software
Key Software Products offers a number of other products for
BBS's:
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 3
1.1.1 KSP Telnet
A door program that allows callers to connect to remote
computers anywhere on the Internet via your BBS. Available now
on our BBS.
1.1.2 KSP FTP
A door program that allows callers to transfer files to/from
remote computers anywhere on the Internet via your BBS.
1.1.3 KSP SLIP
A door program that allows callers to run any TCP/IP software
from home, including using Mosaic to browse the World Wide Web.
Available now on our BBS.
1.1.4 KSP Mail
A Multi-Threaded Server for SMTP Mail and NNTP Usenet news.
Replaces UUCP, its monthly fees, and slow transfer rates! No
more unwanted newsgroups! Instant mail without waiting for
scheduled events! Works with any BBS software that presently
uses UUCP. Requires a 24hr TCP/IP Internet connection. Can now
receive NNTP news feeds!
1.1.5 So Many CD's
A PCBoard PPE to handle off-line CD-Roms. Seamlessly integrated
into PCBoard. Users post requests for off-line files and have
then returned as attachments to messages. Configurable message
pack-out dates automatically keep your hard disk from getting
cluttered. Available now on our BBS.
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 4
CHAPTER 2 - INSTALLING THE NETWORK CONNECTION FIRST
Before installing KSP-SRVR, you must first install:
1. The network interface hardware.
2. A corresponding packet driver.
3. A packet driver shim (if needed).
Detailed directions for these preliminary steps are available in
separate documentation that comes with the corresponding
hardware or software.
It's most common that multi-node BBS's are interconnected with
Ethernet and either Lantastic or Novell. Unfortunately, these
two network operating systems were designed using their own
proprietary protocols rather than the TCP/IP protocol and their
own proprietary software rather than packet drivers to talk to
their Ethernet interface cards. However, a piece of software
called a packet driver "shim" can be used to let both TCP/IP and
their proprietary protocol coexist.
2.1 Packet Driver Shim for Novell
Novell's network software is installed in layers as TSRs in the
order shown below. These commands are usually found either in
the AUTOEXEC.BAT file or in another batch file in a directory
typically called C:\NWCLIENT.
LSL
NE2000 }-- specific to your interface card
IPXODI
VLM
The packet driver shim (ODIPKT) logically sits on top of IPXODI,
providing a packet driver interface for software such as
KSP-SRVR:
LSL
NE2000 +--- Frame Type (0-3)
IPXODI |
ODIPKT 2 97 }--- The packet driver shim
VLM |
+----- Packet Vector Interrupt (96-127)
(See comment below about hex vs. decimal)
The ODIPKT command line parameters may vary according to which
version of the software you have and how your hardware is
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 5
configured. The "Frame Type" parameter should correspond to the
position of ETHERNET_II among the frame types specified in
NET.CFG; zero (0) selects the first frame type, one (1) the
second, and so on. The "Packet Vector Interrupt" number should
correspond to an unused interrupt vector. Note that older
versions of ODIPKT insist that this number be given in decimal
(96-127) rather than in hex (0x60-0x7F). The necessary packet
driver shim can be downloaded from the Key Software Products BBS
as file ODI-SHIM.ZIP.
2.2 Packet Driver Shim for Novell w/Token-Ring SNAP
Another shim called ODITRPKT exists for Novell that should be
used if the underlying network is Token-Ring_SNAP. Installation
is similar to ODIPKT as described above, except that the first
command line parameter must correspond to the Token-Ring_SNAP
frame type in NET.CFG, and starts at "1" rather than "0". This
shim can be downloaded from the Key Software Products BBS as
file TKN-SHIM.ZIP.
2.3 Packet Driver Shim for Lantastic
Using a packet driver shim with Lantastic requires that
Lantastic be installed using NDIS (Network Driver Interface
Specification) Support. The necessary packet driver shim can be
downloaded from the Key Software Products BBS as file
DIS-SHIM.ZIP.
NDIS allows you to stack multiple protocols on a single
adapter. This lets you use multiple protocol drivers (such as
LANtastic and TCP/IP) on the same adapter. You can also use
NDIS to include third-party adapters that have NDIS drivers in
your LANtastic network. Supported adapter types include
Ethernet, Token-Ring and ARCNET (R) adapters. The software and
documentation necessary to add NDIS support to an existing
Lantastic network is available free of charge from Artisoft.
Once you have NDIS installed and working with Lantastic, adding
the shim is a simple matter of editing PROTOCOL.INI (part of the
NDIS support) and CONFIG.SYS.
2.3.1 Changes to CONFIG.SYS
With NDIS installed, there will be two device driver lines in
your CONFIG.SYS file that look something like the following:
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 6
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\AEXNDIS.DOS
The file listed in the second line may differ if you are not
using Artisoft's interface card; in that case, this file would
typically be replaced by a NDIS driver supplied by the card
manufacturer.
The packet driver shim itself is installed as a third device
driver after the first two, as in:
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\AEXNDIS.DOS
DEVICE=C:\DRIVERS\DIS_PKT.DOS }--- The packet driver shim
2.3.2 Changes to PROTOCOL.INI
The PROTOCOL.INI file is a text file created (usually in the
C:\LANTASTI directory) as part of the NDIS installation. Before
adding the packet driver shim, it typically looks like the
following, but with the "iobase" and "interrupt" parameters
changed according to your hardware, or with the entire
"[AEXNDIS_NIF]" section replaced if you are not using an
Artisoft interface card.
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
[AEXNDIS_NIF]
DRIVERNAME = AEXNDS$
IOBASE = 0x300
INTERRUPT = 15
Adding the packet driver shim requires adding another section to
the PROTOCOL.INI file:
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
[AEXNDIS_NIF] <---+
DRIVERNAME = AEXNDS$ |
IOBASE = 0x300 |
INTERRUPT = 15 | These names must match!
|
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 7
[PKTDRV] |
DRIVERNAME = PKTDRV$ |
BINDINGS = AEXNDIS_NIF <---+
INTVEC = 0x61
CHAINVEC = 0x66
NOVELL = Y
Note that the name "AEXNDIS_NIF" must exactly match the spelling
used as the title of the previous section, "[AEXNDIS_NIF]"; if
you are not using Artisoft interface cards, then both occurences
will use some other identifier. The "INTVEC" parameter may be
anything from 0x60 to 0x80; you may have to experiment to find
an unused interrupt number.
2.4 Packet Driver Shim for Banyan Vines
Although Key Software Products has never used it, and thus
cannot offer help on its installation, a packet driver shim does
exist for Banyan Vines and can be downloaded from the Key
Software Products BBS as file BAN-SHIM.ZIP.
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 8
CHAPTER 3 - THE WATTCP CONFIGURATION FILE
In order to run, KSP-SRVR and KSP-NODE need to know some
information about your network and BBS configuration, and tries
to find this in a configuration file called WATTCP.CFG.
KSP-SRVR and KSP-NODE look in three directories to locate this
file. First, they check for an environment variable called
WATTCP.CFG that specifies the directory. Second, they look in
the current (default) directory. Third, if still not found,
they look in the directory that contains the executable
(KSP-SRVR.EXE or KSP-NODE.EXE).
The following example may be helpful for those using the
environment variable approach: If you place WATTCP.CFG in your
PCB directory, then your AUTOEXEC.BAT file should contain the
following command:
set WATTCP.CFG=C:\PCB
Note that there is no trailing "\" after the directory name!
If KSP-SRVR or KSP-NODE still can't find the configuration file,
they will attempt to automatically configure by looking for a
"BOOTP" server on your network. Most BBSs will not have a BOOTP
server, so we do not recommend this approach. We only mention
it here because it explains why you'll get a message saying
"Configuring through BOOTP" if it can't find your configuration
file.
The WATTCP.CFG configuration file is a normal text file
containing one entry per line. A sample configuration file is
included in this distribution, but the values MUST be modified
to suit your particular environment or else KSP-SRVR and
KSP-NODE will not work!
The syntax of every entry follows the following format:
[ directive = [ "data" | data ] ] [ # comment | ; comment ]
I.e., if a directive is not followed by data, the directive is
ignored. Similary, lines without directives are ignored. The
directive is NOT case sensitive; the data IS case sensitive.
e.g., netmask=255.255.252.0
domainslist=ksp.com ; Our domain
Whitespace is normally removed from data; data containing blanks
must be surrounded by quotes. An unquoted '#' or ';' marks the
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 9
beginning of a comment.
3.1 Network Parameters
The following parameters control how KSP-SRVR communicates with
the rest of the TCP/IP network.
3.1.1 The PC's Host Name
This is the network name of the PC that runs KSP-SRVR.
Example: hostname=bbs
Note that the host name does not include the domain name
suffix. For example, the hostname of machine '"bbs.ksp.com" is
simply "bbs".
3.1.2 The PC's Domain Name
This is the network name of the subnet to which your PC (and
possibly others) are connected.
Example: domainslist=ksp.com
Note that the domain name does not include the host name
prefix. For example, the domain name of machine '"bbs.ksp.com"
is "ksp.com".
3.1.3 The PC's IP Address
This is the unique IP address assigned to your KSP-SRVR
machine. It is the one Telnet users will use when trying to
connect to your BBS through the Internet. (They may also use
the hostname.domainname format if supported by your nameserver.)
Example: my_ip=100.2.37.4
Note: As an alternative, you may also set the IP address using
an environment variable, as in:
set ksp-ip=100.2.37.4
NOTE: An "IP address" is a logical addressing scheme used on
TCP/IP networks such as the Internet. Each computer connected
to the Internet is assigned a unique IP address. Your local
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 10
network "guru" or access provider should be able to provide you
with the IP addresses you need.
IMPORTANT: The IP addresses given in this document are only
examples. Do NOT attempt to use them - they will NOT work and
your network administrator will probably get VERY upset!
3.1.4 The Name Server's IP Address
This is the unique IP address assigned to a network name
nerver. You may specify more than on nameserver by using more
than one "nameserver" line.
Example: nameserver=111.21.108.110
Your local network "guru" or access provider should be able to
provide you with the proper IP addresses of appropriate network
name servers.
3.1.5 The Router's IP Address
This is the unique IP address assigned to the network router.
Syntax: gateway = ipaddr [ , subnet [ , subnet_mask ] ]
Examples: gateway=129.97.176.1
gateway=129.97.176.2,129.97.0.0
gateway=129.97.176.2,129.97.0.0,255.255.0.0
Usually the (destination) subnet and subnet mask need not be
specified, and is used to create a "default". The other forms
are used to specify one or more other gateways for particular
subnets.
Your local network "guru" or access provider should be able to
provide you with the proper IP address of the network router.
3.1.6 The PC's Network Mask
Network masks are used to distinguish destination IP addresses
that are on the local subnet from those that are not. This
option may not be required, depending on your network topology.
Example: netmask=255.255.254.0
Your local network "guru" or access provider should be able to
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 11
provide you with the proper netmask if needed.
3.2 TCP/IP Parameters (optional)
KSP-SRVR will work without using the following parameters, but
they are provided if you wish to change them.
3.2.1 Timeouts
Most network operations (such as establishing a connection to a
remote host) have a maximum time before a timeout error occurs.
The default value is 30 seconds; a smaller value is unwise, but
larger values may be necessary for particularly bad
connections.
Example: sockdelay=40
3.2.2 Maximum Segment Size (MSS)
The default value of MSS is 1400. If you know what maximum
segment size means and know what size you want, you can change
it:
Example: mss=512
Note: Some Internet access providers configure their
dial-up slip and ppp accounts with a very small segment
size. You may need to set mss as low as 212 if your
Internet connection is through such a connection.
3.3 Parameters Specific to KSP Host
Two parameters in the WATTCP.CFG configuration file are specific
to the operation of KSP-SRVR. Each follows the syntax:
ksp-srvr.<parameter_name>=<value>
3.3.1 The Log File Directory
Syntax: ksp-srvr.log_directory=<directory_spec>
Example: ksp-srvr.log_directory=c:\ksp
Purpose: Specifies the directory where the file KSP-SRVR.LOG is
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 12
stored. Each entry is made using the following format:
<date>,<time>,<client>,<minutes>,<node_id>
Comment: This parameter is optional; if not specified, no log
file will be created.
3.3.2 Retrieving Hostname of Remote Client
Syntax: ksp-srvr.retrieve_hostnames=<option>
Example: ksp-srvr.retrieve_hostnames=disabled
Purpose: If left enabled, IP addresses of remote clients will be
translated into hostnames using the domain name server
to provide a reliable identification. Otherwise, only
IP addresses will be used. Affects both the display
and the log files.
Comment: Default is enabled.
All remaining parameters in the WATTCP.CFG configuration file
are BBS node-specific. These parameters follow the syntax:
ksp-node.<parameter_name>=<value>
or: ksp-node[<id_range>].<parameter_name>=<value>
where "<id_range>" is either a single ID number or a pair of ID
numbers separated by a dash. Parameters specified by the first
form apply to all BBS nodes; parameters specified by the second
form apply only to those BBS nodes whose IDs match the specified
range.
Note that when more than one entry applies to the same node, the
last entry prevails; thus the first form can be used to specify
a default for all BBS nodes, followed by use of the second form
to specify exceptions.
3.3.3 Specifying the Fossil Ports
Syntax: ksp-node[<node_range>].fossil_ports=<port_range>
Example: ksp-node[11-20].fossil_ports=1
or: ksp-node[5].fossil_ports=0-3
Purpose: Specifies the range of Fossil port numbers used by one
or more BBS nodes. There should be one fossil port for
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 13
each BBS node running on the same machine.
Comment: Fossil port numbers typically start at 0 (for COM1).
3.3.4 Specifying the Buffer Size
Syntax: ksp-node[<node_range>].buffer_size=<bytes>
Example: ksp-node[11-20].buffer_size=512
Purpose: Specifies the buffer size provided by KSP-NODE for one
or more BBS nodes.
Comment: This parameter is optional. If not specified, KSP-NODE
will use the same buffer size (not "buffer") as the
Fossil driver.
3.3.5 Maximum Number of Rings
Syntax: ksp-node[<id_range>].maxrings=<number>
Example: ksp-node.maxrings=3
ksp-node[5-10].maxrings=0
Purpose: Specifies the maximum number of rings to send to the
BBS when trying to establish a connection.
Comment: Set this value to zero for those nodes which configure
their modems for auto-answer.
3.3.6 Sending a "CONNECT" string to the BBS
Syntax: ksp-node[<id_range>].connect_string=<response>
Example: ksp-node.connect_string="CONNECT 14400/V32/LAPM.V42BIS^M^M"
ksp-node[5-10].connect_string="+FDM^M^MCONNECT 14400^M^M"
Purpose: Specifies the connect string sent to the BBS when a
telnet connection has been established.
Note: The quotation marks are required immediately after the
equals sign and at the end of the line to enclose the
string pair since the string includes a blank.
Carriage return followed by line feed is represented by
the pair of characters, "^M".
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 14
3.3.7 Specifying Modem Delay
Syntax: ksp-node[<node_range>].modem_delay_seconds=<seconds>
Example: ksp-node[11-20].modem_delay_seconds=60
Purpose: It usually takes several seconds from the moment that a
modem detects a ring before the carrier is negotiated
and a connection is established. During this period,
the "carrier detect" signal from the modem is still
inactive and cannot be used to cause inbound Telnet
connections to be refused by that BBS node. To solve
this problem, KSP-NODE ignores all connection requests
from KSP-SRVR for a specified number of seconds after
any modem activity (such as a ring). This parameter
specifies that time period for one or more BBS nodes.
Comment: This parameter is optional. Default is 30 seconds. If
the modem is configured for auto-answer, set this value
for that node to zero.
3.3.8 Disabling Automatic Load High
Syntax: ksp-node[<node_range>].loadhigh=disabled
Example: ksp-node[11-20].loadhigh=disabled
Purpose: KSP-NODE will try to load into an upper memory block
(UMB) if possible. This parameter disables that option
for one or more BBS nodes.
Comment: This parameter is optional. Default is enabled.
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 15
CHAPTER 4 - Programs in the KSP Host Package
There are three programs in the KSP Host package: KSP-NODE,
KSP-SRVR, and KSP-CALL. The purpose and installation of each is
described below.
4.1 KSP-NODE (Installed on each BBS Machine)
KSP-NODE is a small Terminate and Stay Resident (TSR) program
installed on one or more BBS machines. It provides an extension
to the services provided by a Fossil driver, and so must be
installed after the Fossil driver and before running the BBS
program.
For the duration of a telnet session, KSP-NODE keeps the modem
off-hook so that node will look busy to modem callers.
KSP-NODE creates a small buffer for each serial port supported
by the Fossil driver. In addition to the buffers, KSP-NODE
needs about 2,000 bytes of code space. The size of the buffers
can be specified as desired, but is typically around 512 bytes.
4.1.1 Command Line Parameters
KSP-NODE requires one (and optionally two) command line
parameters. The first is a unique ID number assigned to that
machine. If you are multitasking several nodes on one machine,
then a second parameter is required, and together the two
specify a range of ID numbers for all nodes on that machine.
For example:
KSP-NODE 4 8
│ │
│ └── Last ID#
└───── First ID#
You may use your regular BBS node numbers for these ID numbers,
although that is not required. The only real requirement is
that no two BBS nodes share the same ID. The ID numbers are
used in the WATTCP.CFG configuration file (see above) to specify
certain configuration parameters that apply to specific BBS
nodes.
If you are multi-tasking under DESQview, then you should add the
"/DV" command line parameter so that KSP-NODE will let other
processes run while it is waiting on the network:
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 16
KSP-NODE /DV 4 8
│ │
│ └── Last ID#
└───── First ID#
4.2 KSP-CALL (Used to Test KSP-NODE)
KSP-CALL is a small utility program intended to be used to
verify proper installation of KSP-NODE. Basically, KSP-CALL is
sort of a NetBios version of a Telnet client program. That is,
you may run it to log into any of your BBS nodes where KSP-NODE
has been installed.
KSP-CALL and KSP-NODE communicate via NetBios, and thus work
only within the limits of your own local area network (i.e.,
within the context of your Novell or Lantastic network).
4.2.1 Command Line Parameters
If no command line parameter is given, KSP-CALL will select an
idle BBS node and establish a connection with it. Otherwise,
you may specify a BBS node's ID number on the command line and
KSP-CALL will try to establish a connection with that node.
4.3 KSP-SRVR (The Inbound Telnet Server)
KSP-SRVR acts like a telephone switchboard. It accepts inbound
Telnet calls from the Internet and then uses NetBios to route
them to KSP-NODE on an idle BBS node. KSP-SRVR can handle
several Telnet sessions at the same time. The actual number
depends on memory requirements (see below), but in practice the
usual limit is about sixteen simultaneous sessions.
4.3.1 Command Line Parameters
KSP-SRVR has two command line parameters; both are optional. If
specified, the first is the maximum number of simultaneous
sessions and the second is the per-session buffer size. Memory
requirements increase as the product of sessions and buffer
size; the larger the buffer size, the fewer the number of
simultaneous sessions that can be supported. The default is 16
sessions and a buffer size of 512 bytes.
Note: Unlicensed (evaluation) copies of KSP-SRVR are limited to
a single session, five minutes per session, and a total of 15
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 17
minutes running time. These restrictions are removed with the
purchase of an "access key" (see ORDERFRM.DOC).
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 18
CHAPTER 5 - SPECIAL CONFIGURATION CONSIDERATIONS
There are two common software environments that deserve special
mention. When running any of the KSP-HOST software under one of
these environments, there are some additional configuration
steps required.
5.1 PCBoard
There are two versions of PCBoard that run under MS/DOS:
PCBOARD.EXE and PCBOARDM.EXE. The latter is the "Multi-Port"
version, and is the only one that can be used with a Fossil
driver (required by KSP-NODE).
You can tell whether or not PCBoard is configured to use the
fossil driver because it will display "PORT1F" instead of "COM1"
(for example) on the waiting for calls screen.
Don't forget that PCBoard uses port numbers which are one
greater than those used by Fossil drivers. For example, Fossil
designates COM1 and COM2 as port 0 and port 1 respectively. Yet
PCBoard thinks of these as port 1 and port 2.
5.2 DESQview
To run any software based on the Waterloo TCP/IP library under
DESQview, it's absolutely necessary to install a packet
multiplexer on top of the packet driver or packet driver shim
before starting DESQview. This is necessary whenever running
more than one program on the same machine, even if only one of
them is a Waterloo TCP/IP product. A freeware packet
multiplexer is available from Key Software Products as file
KSPMUX*.ZIP, where the "*" is a two-digit version number.
To run the KSP-HOST software under DESQview, you must also
enable NETBIOS support. To do so, run DVSETUP inside DESQview.
Select "Advanced Setup", and press "N" for "Network". Then
enter "Y" under "NETBIOS" and press return twice to save and
exit.
5.3 Novell
NetBios support on Novell networks is provided by a TSR called
"NETBIOS". You must install this TSR before running any KSP-HOST
software. (Lantastic networks already have NetBios support
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 19
built into the basic system.)
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 20
APPENDIX 1 - HOW TO REACH US
The Key Software Products BBS/FAX number (415-364-9847) operates
24 hours a day, 7 days a week. Software at our end
automatically determines whether an incoming call is data or FAX
and will operate accordingly.
If you have access to electronic mail, you can send us a message
via any of the following:
On COMPUSERVE, send mail to:
>Internet:tech.support@ksp.com
On PRODIGY, send mail to: VGDC59A
On Internet, UUCP, or Bitnet, send mail to:
tech.support@ksp.com
On Fidonet, address mail to "UUCP" at nearest fidonet site which
provides a gateway to Internet, such as 1:105/42.
1st line of message: To: tech.support@ksp.com
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 21
APPENDIX 2 - GETTING UPDATES VIA THE INTERNET
The main distribution file is KSPHST??.ZIP, where "??" is the
version number. You can retrieve this file via anonymous ftp at
"scizzl.scu.edu", directory "ksp". Please note that there is no
"e" at the end of "scizzl".
This file is also available from the KSP BBS, either by calling
in and downloading, or via e-mail using the "LISTSERV"
capabilities of the BBS.
To use LISTSERV, you must send a message addressed to the
Internet address listserv@ksp.com. The message must contain an
LISTSERV command entered as a single line of text, and it must
be the first line in the message. The LISTSERV commands that are
supported include:
Command: HELP tlbmm-l
Purpose: Returns an text file with help information about LISTSERV.
Command: DIR tlbmm-l
Purpose: Returns an e-mail message listing all of the file
directories on the BBS by number and description.
Command: LIST tlbmm-l 1
Purpose: Returns an e-mail message listing all of the files in
directory #1 of the BBS.
Command: GET tlbmm-l KSPHST12.ZIP
Purpose: Returns an e-mail message containing a uuencoded version of
the file KSPHST12.ZIP. To extract the file, you must save
the message as a file on your system, edit out the e-mail
header at the beginning of the file, and then use a program
called UUDECODE (commonly available on Unix) to convert the
uuencoded version back to the original ZIP format, and then
(finally) use PKUNZIP to extract the contents of the file.
Copyright (C) 1995-96, Key Software Products. All Rights Reserved
Feb 11, 1996 KSP-HOST (tm) v1.2 22
APPENDIX 3 - LEGAL STUFF
LIMITED WARRANTY
This software is provided 'as is' without warranty of any kind,
either expressed or implied, including, but not limited to the
implied warranties of merchantability and fitness for a
particular purpose. The entire risk as to the quality and
performance of the program is with you.
Some states do not allow the exclusion of implied warranties, so
the above exclusions may not apply to you. This warranty gives
you specific legal rights and you may also have other rights
which vary from state to state.
Key Software Products has taken due care in preparing the
documentation and software included in to ascertain their
correctness and effectiveness. However, Key Software Products
does not warrant that operation of this software will be
uninterrupted or error free. In no event shall Key Software
Products be liable for incidental or consequential damages in
connection with or arising out of the furnishing, performance,
or use of this software.
LICENSE
You MAY use this software on any computer or computers in your
possession. The licensed version is registered for use on up to
a fixed number of BBS nodes running on multiple machines and/or
multiple multi-tasking processes.
You MAY copy this software into any machine readable or printed
form for backup or modification purposes in support of your use
of the software.
You MAY distribute the original unmodified, unlicensed version
of this software, but you may not charge a fee exceeding $5.00
to cover the cost of duplicating, shipping, and handling. You
may NOT distribute a licensed version of this software.
You may NOT use, copy, modify, sublicense, assign or transfer
this software and its license, or any copy or modification, in
whole or in part, except as expressly provided for in this
license.
Copyright (C) 1995-96, Key Software Products. All Rights Reserved